Enterprise classified document service

ABSTRACT

A method of maintaining a classified document labeling policy of an institution. One or more documents are received and document types are determined therefor. A determination is made as to whether the documents comply with the classified document labeling policy of the institution using one or more rules. The rules embody the classified document labeling policy of the institution in a computer interpretable form and are dependent upon document type. Corrective measures for ones of the documents determined to be non-compliant are taken.

BACKGROUND

The present disclosure relates generally to document processing. Itfinds particular application in conjunction with identifying classifieddocuments, and will be described with particular reference thereto.However, it is to be appreciated that the present exemplary embodimentsare also amenable to other like applications.

Most large institutions have a defined process for labeling classifieddocuments. Classified documents are typically documents that includeconfidential and/or business sensitive data, whereby they are intendedto have controlled access and distribution. Further, classifieddocuments normally have a defined retention policy. One problem withclassified documents is that the process for labeling them is oftenunwieldy. As such, authors of documents often do not understand and/orare not familiar with the process of labeling classified documents,which often leads to a failure to label documents and/or incorrectlylabeling documents.

The present disclosure provides a new and improved system and methodwhich overcome the above-referenced problems and others.

BRIEF DESCRIPTION

According to aspects illustrated herein, a method is provided ofmaintaining a classified document labeling policy of an institution. Oneor more documents are received and document types are determinedtherefor. A determination is made as to whether the documents complywith the classified document labeling policy of the institution usingone or more rules. The rules embody the classified document labelingpolicy of the institution in a computer interpretable form and aredependent upon document type. Corrective measures for ones of thedocuments determined to be non-compliant are taken.

According to further aspects illustrated herein, a classified documentsystem is provided for maintaining a classified document labeling policyof an institution. The system includes a classification engine thatdetermines document types for one or more documents. The system furtherincludes a rules engine that determines whether the documents complywith the classified document labeling policy of the institution usingone or more rules. The rules embody the classified document labelingpolicy of the institution in a computer interpretable form and aredependent upon document type. The system further includes a controllerthat receives the documents and takes corrective measures for ones ofthe documents determined to be non-compliant.

According to further aspects illustrated herein, a user device includinga classified document module for maintaining a classified documentlabeling policy of an institution is provided. The user devices includesa memory and a processor. The memory includes computer executableinstructions that monitor the user device in real time for authoringand/or sharing of documents, determine document types for one or moredocuments being authored and/or shared, determine whether the documentscomply with the classified document labeling policy of the institutionusing one or more rules, and take corrective measures for ones of thedocuments determined to be non-compliant. The rules embody theclassified document labeling policy of the institution in a computerinterpretable form and are dependent upon document type. The processorexecuting the computer executable instructions.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an information technology (IT)infrastructure for an institution;

FIG. 2 is a detailed block diagram of a classified document system(CDS); and,

FIG. 3 is a flow chart of a method of evaluating documents to determinewhether they should be labeled as classified.

DETAILED DESCRIPTION

With reference to FIG. 1, an information technology (IT) infrastructure100 for an institution is provided. It is contemplated that theinstitution is one of a business institution, an academic institution, agovernment institution, and the like. The IT infrastructure 100 includesa document storage system (DSS) 102, an electronic messaging system(EMS) 104, one or more user devices 106, a classified document system(CDS) 108, and the like. In certain embodiments, it is contemplated thatthe DSS 102 and the CDS 108 are part of a common document system (notshown). Suitably, the components of the IT infrastructure 100 areinterconnected via a communications network 110, such as the Internet, alocal area network, a wide area network, a wireless network, or thelike.

The DSS 102 is a repository of documents generated throughout theinstitution and includes one or more documents, such as emails, webpages, text documents, spreadsheet documents, images, and the like. Thedocuments may be stored in one or more of an image format, an electronicformat, or the like. In certain embodiments, each of the documentsincludes document properties, such as creation date, modification date,classified status, retention policy, and the like. The DSS 102 suitablyallows remote access to the documents over the communications network110.

In certain embodiments, the DSS 102 maintains a profile of searchableMeta data for each of the documents. It is contemplated that the profilefor each of the documents includes one or more of a description of thedocument, a title of the document, a document type, one or more of thedocument properties, and the like. Document type is the granularity withwhich the classified document labeling policy refers to documents.Additionally or alternatively, in certain embodiments, the DSS 102maintains an audit log. The audit log tracks actions performed on theDSS 102 by, for example, users and/or devices of the IT infrastructure100. It is contemplated that these actions include one or more ofmodification of document content, deletion of a document, modificationof document Meta data, modification of a document location, copying adocument, and the like.

One or more databases 112 and/or one or more servers 114 typicallyembody the DSS 102. The databases 112 store the documents, and, incertain embodiments, the Meta data and/or the audit log. The databases112 include relational databases, file systems, and the like. Theservers 114 facilitate remote access to the documents via thecommunications network 110 and, when applicable, searching of the Metadata. In certain embodiments, the servers 114 include documentmanagement servers, file servers, file repository servers, and the like.The databases 112 and/or the servers 114 are typically centrally locatedwithin the IT infrastructure 100 of the institution. However, it iscontemplated that the databases 112 and/or the servers 114 aredistributed throughout the IT infrastructure 100 at varying locationstherein.

Each of the servers 114 includes a communication unit 116, a memory 118,a processor 120, and the like. The communications units 116 provide theservers 114 with interfaces from which to interact with the databases112 and/or each other 114, optionally via the communications network110. The communications units 116 further allow the servers 114 tointeract with other components of the IT infrastructure 100, such as theuser devices 106, via the communications network 110. The memories 118include computer executable instructions for performing the above notedfunctions associated with the servers 114, such as allowing remoteaccess to the documents. The processors 120 execute the computerexecutable instructions on the memories 118 to perform the above notedfunctions.

The EMS 104 allows users and/or devices of the IT infrastructure 100,such as the user devices 106, to send and/or receive messagesaccompanied by documents to and/or from other users and/or devices ofthe IT infrastructure 100. In certain embodiments, the EMS 104 furtherallows users and/or devices of the IT infrastructure 100 to send and/orreceives messages accompanied by documents to and/or from users and/ordevices external to the IT infrastructure 100. For example, the EMS 104allows a user of the IT infrastructure 100 to send an email with anattached document to a party external to the IT infrastructure 100 overthe Internet. Additionally or alternatively, in certain embodiments, theEMS 104 maintains an audit log. The audit log tracks actions performedon the EMS 104, including documents sent via the EMS 104.

One or more databases 122 and/or one or more servers 124 typicallyembody the EMS 104. The databases 122 store the messages sent throughand/or received via the EMS 104. Additionally or alternatively, thedatabases 122 store the audit log. The servers 124 facilitate thereceipt and transmission of messages via the communications network 110.In certain embodiments, the servers 124 include email servers, instantmessage servers, and the like. As with the DSS 102, the databases 122and/or the servers 124 are typically centrally located within the ITinfrastructure 100 of the institution. However, it is contemplated thatthe servers 124 and/or the databases 122 are distributed throughout theIT infrastructure 100 at varying locations therein.

Each of the servers 124 includes a communication unit 126, a memory 128,a processor 130, and the like. The communications units 126 provide theservers 124 with interfaces from which to interact with the databases122 and/or each other 124, optionally via the communications network110. The communications units 126 further allow the servers 124 tointeract with other components of the IT infrastructure 100, such as theuser devices 106, via the communications network 110. The memories 128include computer executable instructions for performing the above notedfunctions associated with the servers 124, such as allowing remoteaccess to the documents. The processors 130 execute the computerexecutable instructions on the memories 128 to perform the above notedfunctions associated with the servers 124.

The user devices 106 allow associated users to read and/or writedocuments within the IT infrastructure 100, optionally via thecommunications network 110. It is contemplated that these documents arestored local to the user devices 106 and/or on the DSS 102. In certainembodiments, the user devices 106 further allow associated users tomessage documents within the IT infrastructure 100 via the EMS 104and/or print documents within the IT infrastructure 100. To simply thesetasks, the user devices 106 suitably include graphical user interfaces.For example, it is contemplated that a graphical user interface of oneof the user devices 106 allows an associated user to read a documentlocated on the DSS 102 and, optionally, print the document.

The user devices 106 are digital processing devices, such as computers,smart phones, personal digital assistants, and the like, executingsoftware to carry out the above noted functions. That is to say, theuser devices 106 are digital processing devices executing software toallow users associated with the user devices 106 to read and/or writedocuments and, in certain embodiments, message and/or print documents.For example, it is contemplated that a word processing program, such asMICROSOFT WORD, executing on the user devices 106 facilitates thereading and/or writing of documents. As another example, it iscontemplated that an email program, such as MICROSOFT OUTLOOK,facilitates the messaging of documents.

Each of the user devices 106 suitably includes a communications unit132, a memory 134, a display 136, a user input device 138, a processor140, and the like. The communications units 132 allow the user devices106 to interact with other components of the IT infrastructure 100, suchas the DSS 102 or the CDS 108, via the communications network 110. Thememories 134 include computer executable instructions for performing theabovenoted functions associated with the user devices 106, such asreading and/or writing documents. The displays 136 display the graphicaluser interfaces facilitating user interaction with the user devices 106.The user input devices 138 allow users to interact with the graphicaluser interfaces. The processors 140 execute the computer executableinstructions on the memories 134.

In certain embodiments, each of one or more of the user devices 106further includes a classified document module (CDM) 142. The ones of theuser devices 106 including a CDM are hereafter referred to as thesubscribed user devices. The CDMs 142 are suitably embodied by computerexecutable instructions to be executed by the processors 140, but it iscontemplated that the CDMs 142 are hardware. An IT administratorsuitably installs the CDMs 142 on the subscribed user devices, but it iscontemplated that viral and/or trolling technology is used to installthe CDMs 142 on the subscribed user devices. For example, it iscontemplated that flaws in an operating system of a subscribed userdevice are exploited to install a CDM.

One or more of the CDMs 142 scan associated subscribed user device fordocuments. It is contemplated that this scanning is triggeredperiodically by, for example, a timer event, a network event (from, forexample, the CDS 108), or the like. Further, it is contemplated that thedocuments the CDMs scan for include one or more of all documents,documents created and/or modified within a predetermined number of pastdays, documents that have not been evaluated before, and the like. Uponlocating a document, a CDM evaluates the document to determine whetherit complies with classified document rules of the institution. Theclassified documents rules embody the classified document labelingprocess in a computer interpretable form.

Additionally or alternatively, one or more of the CDMs 142 monitorassociated subscribed user devices on an ongoing basis for the authoringand/or sharing of documents. It is contemplated that authoring includescreating and/or modifying documents. Further, it is contemplated thatsharing includes printing documents and/or messaging documents via, forexample, the EMS 104. Upon detecting the authoring and/or sharing of adocument, a CDM evaluates the document to determine whether it complieswith the classified document rules of the institution. For example, whena document is emailed or printed, the document is evaluated. In the caseof sharing, the evaluation is suitably performed before the document isactually shared (e.g., emailed or printed).

Additionally or alternatively, one or more of the CDMs 142 are receptiveto user input triggering an evaluation of a document. For example, agraphical user interface for authoring documents includes an option,such as a button or menu entry (possibly denoted “Compliance Checker”),to evaluate a document. It is contemplated that, in certain embodiments,this operates similar to the spell-check feature commonly found in wordprocessing programs, such as MICROSOFT WORD. As above, the evaluationseeks to determine whether the document complies with the classifieddocument rules of the institution

To evaluate a document, a CDM submits the document to the CDS 108 viathe communications network 110, where the CDS 108 evaluates the documentusing the classified document rules and returns the results thereof.Results include whether a document complies with the classified documentlabeling policy of the institution and, optionally, a confidence level.Alternatively, to evaluate the document, the CDM locally evaluates thedocument through the use of the classified document rules of theinstitution. Suitably, the classified document rules are remotelylocated in the CDS 108, but it is contemplated that the classifieddocument rules are local and/or stored in another component of the ITinfrastructure 100. The process employed to perform the evaluationlocally is described hereafter in conjunction with the CDS 108.

Regardless of the reason for evaluating a document, in certaininstances, the CDMs 142 take corrective measures upon a determinationthat the document is non-compliant with the classified document labelingprocess of the institution. In certain embodiments, corrective measuresare based on a confidence level of the evaluation. Corrective measuresinclude one or more of modifying the document, deleting the document,moving the document, creating a link to the document, rejecting movementof the document, notifying a user, such as an owner of the document oran IT administrator, updating a document's retention policy, and thelike. Further corrective measures are described hereafter in conjunctionwith the CDS 108.

In certain embodiments, the corrective measures are dependent upon thereason the document was evaluated. For example, if a document wasevaluated because it was being printed and determined to benon-compliant with the classified document rules, the print job could berejected or the document could be printed with a “classified document”symbol. As another example, if a document was evaluated because it wasbeing emailed and determined to be non-compliant with the classifieddocument rules, the email could be rejected or stripped of the document.

The classification engine 108 evaluates documents to facilitatecompliance with the classified document labeling policy of theinstitution. The documents evaluated may be documents found by scanningthe IT infrastructure 100 via, for example, the communications network110. Additionally or alternatively, the documents evaluated may bereceived from components of the IT infrastructure 100, such as the userdevices 106. An evaluation of a document suitably yields a determinationas to whether the document is compliant with the classified labelingpolicy of the institution and, optionally, a confidence level thereof.In certain embodiments, subsequent to an evaluation of a document of theIT infrastructure 100, manual and/or automatic corrective measures aretaken if the document is non-compliant. Additionally or alternatively,in certain embodiments, subsequent to or contemporaneous with a scan ofthe IT infrastructure 100, a report of compliance with the classifieddocument labeling policy of the institution is generated and provided toone or more administrators of the institution. Additionally oralternatively, in certain embodiments, the CDS 108 is employed tocorrect documents in the IT infrastructure 100 when the CDS 108 is firstdeployed, and then the CDMs 142 are employed to maintain documents inthe IT infrastructure 100.

With reference to FIG. 2, a detailed view of the CDS 108 is provided.One or more servers and/or one or more databases typically embody theCDS 108. The servers and/or the databases are typically centrallylocated within the IT infrastructure 100 of the institution. However, itis contemplated that the servers and/or the databases are distributedthroughout the IT infrastructure 100 at varying locations therein. Asillustrated, the CDS 108 includes a rules database 144, a controller146, a classification engine 148, a rules engine 150, a communicationsunit 152, and a memory 154.

The rules database 114 includes one or more rules embodying theclassified document labeling policy of the institution in a computerinterpretable form. In certain embodiments, the classified documentlabeling policy further encompasses retention policies for classifieddocuments. The rules are suitably provisioned to determine a document'scompliance with the classified document labeling policy given one ormore parameters. These parameters include one or more of document type,creation date, modification date, document content, Meta data of thedocument, and the like.

The controller 146 scans the IT infrastructure 100 for documents toevaluate via the communications network 110. The scanning is suitablytriggered at periodic intervals by, for example, a timer event. However,other trigger events are contemplated. For example, an IT administratorof the IT infrastructure 100 may initiate the scanning. As anotherexample, scanning may be automatically initiated when the CDS 108 isfirst deployed to process existing documents in the IT infrastructure100. In certain embodiments, the documents the controller 146 scans forinclude one or more of all documents, documents created and/or modifiedwithin a predetermined number of past days, documents that have not beenevaluated before, and the like. The scanning includes scanning one ormore of the DSS 102, the EMS 104, and the user devices 106. It iscontemplated that, in certain embodiments, the controller 146 scans theuser devices 106 by providing the CDMs 142 of the user devices 106 withnetwork events instructing them to scan their associated user device fordocuments and, optionally, return found documents. As noted above, theCDMs 142 may employ trolling and/or viral technology.

Additionally or alternatively, the controller 146 listens on thecommunications network 110 for documents to evaluate. Documents receivedvia the communications network 110 are typically received from the CDMs142. However, it is contemplated that documents are received from otherdevices of the IT infrastructure 100. As noted above, the CDMs 142 mayprovided documents in response to requests therefor from the controller146 or asynchronously by, for example, timer events of the CDMs 142.

Upon receiving or locating a document to evaluate, the controller 146employs the classification engine 148 to determine a document type forthe document. Document type is suitably the granularity with which theclassified document labeling policy refers to documents. It is importantto note the distinction between “classified documents” and “documentclassification”. The latter refers to determining document type, such asan IRS 1040 form, a birth certificate, an auto loan application, and thelike, whereas the former refers to determining if a document containssensitive data, irrespective of document type. The classification engine148, in addition to determining a document type, optionally determines aconfidence level as to determined document type. In certain embodiments,the classification engine 148 uses XEROX SMART DOCUMENT TECHNOLOGIES(SDT) and/or commercial classification software, such as XIG CATEGORIXand KOFAX INDICIUS. Further, the classification engine 148 is suitablyembodied by computer executable instructions, but hardware iscontemplated.

Before the controller 146 or any other component of the CDS 108 use theclassification engine 148, it is trained on a set of exemplar documents.The exemplars include one or more exemplar documents for each documenttype to be classified. Notably, however, the more exemplars in thetraining set, the more accurate the classification engine 148 will be.In certain embodiments, as documents types for documents passed to theclassification engine 148 are confirmed by, for example, user input,these documents are added to the training set of exemplars. Documenttypes may be confirmed in bulk by, for example, an IT administrator.Advantageously, expanding the training set allows refinement of theclassification engine 148.

After identifying the document type, the controller 146 employs therules engine 150 to determine whether the document is in compliance withthe classified document labeling process of the institution. If thedocument has not been classified, this includes determining whether thedocument should be marked as classified. If the document is alreadyclassified, this includes determining whether the document is properlyclassified. For example, the author of the document may have marked thedocument as classified when it should not have been so marked. Asanother example, the author of the document may have been properlymarked as classified when the document was created, but a sufficientamount of time has lapsed that the document need not be marked asclassified any longer.

To make the abovenoted determinations, the rules engine 150 uses therules in the rules database 144. These rules embody the classifieddocument labeling process of the institution in a computer interpretableform. For example, it is contemplated that a rule in the rules database144 specifies that a draft patent application is to be markedconfidential for a year. Further, the rules are suitably dependent uponone or more parameters, such as document type, document creation date, adate within the document, Meta data associated with the document, andthe like. As with the classification engine 148, the rules engine 150optionally returns a confidence level as to the determination. Incertain embodiments, the confidence level is dependent upon theconfidence level of the classification engine 148. Further, the rulesengine 150 is suitably embodied by computer executable instructions, buthardware is contemplated.

In certain embodiments, subsequent to or contemporaneous with a scan ofthe IT infrastructure 100, the controller 148 generates a reportsummarizing the results of the evaluations. This report is suitablyprovided to one or more administrators of the institution automatically,but it is contemplated that the report is provided to the administratorsin response to a request therefor. The report advantageously allows theadministrators to assess compliance with the classified documentlabeling policy of the institution. Additionally or alternatively,subsequent to an evaluation of a document, manual and/or automaticcorrective measures are taken if the document is non-compliant.

Corrective measures include one or more notifying an IT administrativeservice of the non-compliant document and leaving it to ITadministrative to correct; flagging the document as non-compliant in thefile system; informing the owner of the suspected non-compliance;informing recipients of the document of the suspected non-compliance;automatically correcting the document; and the like. It is contemplatedthat, in certain embodiments, corrective measures are applied based onthe confidence level attributed to a determination of non-compliance.For example, in certain embodiments, the automatic correction isperformed if the confidence level of a document exceeds a certainthreshold.

To notify the owner, the EMS 106, a CDM, or the like may be employed.Typically, the owner is determined based upon Meta data associated withthe document. However, the owner may be determined based upon thelocation of the document within the IT infrastructure 100. For example,if the document is located on Joe's computer, the owner is determined tobe Joe. In certain embodiments, the notice provided to the ownerrequests the owner to determine if the document is non-compliant. If theowner finds the document is compliant, the IT administrative service issuitably notified thereof. If the owner finds the document to benon-compliant, the controller 148 suitably corrects it automatically orleaves it to the owner to correct.

In certain embodiments, the recipients of the document are providednotice similar to the notice provided to the owner of the document. Therecipients of the document are suitably determined through review of theaudit log of the EMS 104. Additionally or alternatively, the recipientsare determined through review of the audit log of the DSS 102. Arecipient in the context of the DSS 102 is one that copied the documentfrom the DSS 102 over the communication network 110.

When automatically correcting the document, if the document wasincorrectly marked as classified, the document is de-classified. If thedocument was not marked as classified, the controller 148 annotates thedocument and/or updates the classified status of the document. Further,in certain embodiments, the controller 148 sets the retention policy ofthe document based on parameters of the document, such as one or more ofthe time stamp for creation, a date included in the document, and thelike. If the document is outside the retention period, the controller148 may refrain from updating the retention policy of the document.

In certain embodiments, the controller 148 looks for copies of thedocument within the IT infrastructure 100 as part of automaticcorrection. This may be performed by doing a general search of the ITinfrastructure 100, as discussed above. Additionally or alternatively,this may be performed by checking the audit logs associated with the DSS102 and/or the EMS 104 to determine if the document was electronicallymessaged to another and/or copied. Insofar as the document waselectronically messaged, a search of a user device of the recipient isoptionally performed. In certain embodiments, this is performed via aCDM. When a copy is found, the controller 148 suitably performs one ofdeleting it, replacing it with the corrected version, moving thecorrected version to the DSS 104 and replacing the copy with a link tothe corrected version on the DSS 104, and the like.

The communications unit 152 allows the CDS 108 to interact with othercomponents of the IT infrastructure 100, such as the DSS 102 and theuser devices 106, via the communications network 110. The memory 154includes computer executable instructions for performing the abovenotedfunctions associated with controller 154, such as scanning the ITinfrastructure 100 for documents. The controller 148 suitably carriesout the computer executable instructions of one or more of the memory154, the classification engine 148, and the rules engine 150.

With reference to FIG. 3, a method 300 of maintaining a classifieddocument policy of the institution is provided. It is contemplated thatthe method 300 is performed by the CDM 142 or the CDS 108. According tothe method 300, one or more documents are received 302 and documenttypes are determined 304 therefor. A determination 306 is made as towhether the documents comply with the classified document labelingpolicy of the institution using one or more rules. The rules embody theclassified document labeling policy of the institution in a computerinterpretable form and are dependent upon document type. Correctivemeasures for ones of the documents determined to be non-compliant aretaken 308.

As used herein, a memory includes one or more of a non-transientcomputer readable medium; a magnetic disk or other magnetic storagemedium; an optical disk or other optical storage medium; a random accessmemory (RAM), read-only memory (ROM), or other electronic memory deviceor chip or set of operatively interconnected chips; an Internet serverfrom which the stored instructions may be retrieved via the Internet ora local area network; or so forth. Further, as used herein, a controllerand/or a processor include one or more of a microprocessor, amicrocontroller, a graphic processing unit (GPU), anapplication-specific integrated circuit (ASIC), a field-programmablegate array (FPGA), and the like; a communications network includes oneor more of the Internet, a local area network, a wide area network, awireless network, a wired network, a cellular network, a data bus, suchas USB and I2C, and the like; a user input device includes one or moreof a mouse, a keyboard, a touch screen display, one or more buttons, oneor more switches, one or more toggles, and the like; and a displayincludes one or more of a LCD display, an LED display, a plasma display,a projection display, a touch screen display, and the like.

It will be appreciated that variants of the above-disclosed and otherfeatures and functions, or alternatives thereof, may be combined intomany other different systems or applications. Various presentlyunforeseen or unanticipated alternatives, modifications, variations orimprovements therein may be subsequently made by those skilled in theart which are also intended to be encompassed by the following claims.

1. A method of maintaining a classified document labeling policy of aninstitution, said method comprising: receiving one or more documents;determining document types for the documents; determining whether thedocuments comply with the classified document labeling policy of theinstitution using one or more rules embodying the classified documentlabeling policy of the institution in a computer interpretable form,wherein the rules are dependent upon document type; and, takingcorrective measures for ones of the documents determined to benon-compliant.
 2. The method according to claim 1, further comprising:scanning an information technology (IT) infrastructure of theinstitution for documents to identify the received documents.
 3. Themethod according to claim 2, wherein the scanning scans user devices ofthe IT infrastructure using viral and/or trolling technology.
 4. Themethod according to claim 1, wherein the received documents includes oneor more document images.
 5. The method according to claim 1, furthercomprising: monitoring a user devices in real time for authoring and/orsharing of documents, wherein the received documents include documentsbeing authored and/or shared.
 6. The method according to claim 5,wherein sharing includes electronically messaging one or more documentsand/or printing one or more documents.
 7. The method according to claim1, wherein the corrective measures include: scanning an informationtechnology (IT) infrastructure of the institution for copies of the onesof the documents determined to be non-compliant.
 8. The method ofaccording to claim 7, wherein the scanning is focused based on one ormore audit logs, wherein the audit logs track actions pertaining to theones of the documents determined to be non-compliant.
 9. The methodaccording to claim 7, wherein the corrective measures include:automatically correcting the ones of the documents determined to benon-compliant; and, one or more of: deleting the copies; replacing thecopies with pointers to the corrected ones of the documents determinedto be non-compliant; replacing the copies with the corrected ones of thedocuments determined to be non-compliant; and, automatically correctingthe copies.
 10. The method according to claim 1, wherein the correctivemeasures include: updating the retention policies of the ones of thedocuments determined to be non-compliant.
 11. The method according toclaim 1, wherein document type is the granularity with which theclassified document labeling policy refers to documents.
 12. The methodaccording to claim 1, wherein classified documents are documentsincluding confidential and/or business sensitive data.
 13. A classifieddocument system for maintaining a classified document labeling policy ofan institution, said system comprising: a classification engine thatdetermines document types for one or ore documents; a rules engine thatdetermines whether the documents comply with the classified documentlabeling policy of the institution using one or more rules, wherein therules embody the classified document labeling policy of the institutionin a computer interpretable form and are dependent upon document type;and, a controller that receives the documents and takes correctivemeasures for ones of the documents determined to be non-compliant. 14.The classified document system according to claim 12, wherein thecontroller scans an information technology (IT) infrastructure of theinstitution to identify the received documents.
 15. The method accordingto claim 12, wherein the corrective measures include: scanning aninformation technology (IT) infrastructure of the institution for copiesof the ones of the documents determined to be non-compliant.
 16. Theclassified document system according to claim 12, further comprising:one or more memories including computer executable instructionsembodying the classification engine and the rules engine, wherein thecontroller executes the computer executable instructions.
 17. A userdevice including a classified document module for maintaining aclassified document labeling policy of an institution, said user deviceincluding: a memory that includes computer executable instructions that:monitor the user device in real time for authoring and/or sharing ofdocuments; determine document types for one or more documents beingauthored and/or shared; determine whether the documents comply with theclassified document labeling policy of the institution using one or morerules, wherein the rules embody the classified document labeling policyof the institution in a computer interpretable form and are dependentupon document type; and, take corrective measures for ones of thedocuments determined to be non-compliant; and, a processor executing thecomputer executable instructions.
 18. The user device according to claim17, wherein sharing includes electronically messaging one or moredocuments and/or printing one or more documents.
 19. The user deviceaccording to claim 17, wherein the corrective measures include one ormore of: denying the sharing of one or more of the ones of the documentsdetermined to be non-compliant; stripping electronic messages includingthe one or more of the ones of the documents determined to benon-compliant before they are sent; and, adding a classified documentsymbol to print jobs of the one or more ones of the documents determinedto be non-compliant.
 20. The user device according to claim 17, whereinthe classified document module uses viral and/or trolling technology.